Database reference guide

HOME

File structure overview

In a traditional Engine system, the main Data Store is referred to as the Engine Repository. A system might contain many Repositories, but only one can be active per installation of Engine at any one time.

Windows Folder Structure

Repository Each Engine Repository corresponds to a windows folder (or directory). The location of this folder is stored in the cerberus.ini file and can be changed via the Engine Administration Utility. To transfer a repository from one system to another, or to copy a repository, simply copy the repository and all it's contents to a new location and point Engine at the new location. Files that are stored at the Repository level are:
  • Link Files
  • @check@ file
  • Extended Security Files

Database A Repository can contain none, one, or many databases. Each Database corresponds to a sub-folder of the repository folder. The maximum number of databases that can be added to a repository is 1024. Files that are stored at the Database level are:

  • Local Links
  • Header Files
  • Table and Column Data Files
  • Index Files

Temp Underneath each Database folder is a TEMP folder. Files stored at this level and below are:

  • Extended Temporary Indexes for columns

Users Each repository contains a USERS sub-folder. A sub-folder is added to the USERS folder for each Engine user that is added to the system. The User folder contains details of temporary objects for that user and is the default output directory for any data output done by the user. The name of the folder is the user's logon name (e.g. the User directory for the SYSTEM user is called SYSTEM) Files contained in the USER directory are:

  • Security files
  • Data export files

A sample Repository structure is shown below:

  Online & Instructor-Led Courses | Training Videos | Webinar Recordings
© Alterian. All Rights Reserved. | Privacy Policy | Legal Notice